Hi Brad,
KMotionCNC Users sometimes have only one C program to Initialize and Home their system. But it shouldn't be a big deal for those to strip out the Homing portion if need be.
Mach3 Users usually always have separate "Reset" and "Home" C Programs.
The Init progam often does other things besides setting parameters such as configuring IO, enabling Axes, DefineCoordSystem(), Enabling Amplifiers, and then often remains in a forever loop to handle things like an MPG, or soft limits, or hardware feedhold inputs, etc...
Hey something you might consider is just reading the Init.c file itself and extracting the parameters.
I've been meaning to do a similar thing for KMotion.exe. The Screen Parameters-> ClipBoard -> Paste into Init.c thing is too confusing and hard to verify the screen settings and the C code are the same. I think we need ScreensToC and CtoScreens buttons that would automatically parse through the C code and import or export the settings for All the Axes.
Regards
TK
| Group: DynoMotion |
Message: 3280 |
From: Brad Murry |
Date: 1/22/2012 |
| Subject: Re: What is the normal sequence of events when initializing a system |
Thanks Tom, Thank does clear things up. As Carl mentioned, its kinda funny that I have written all this code for a device that I am not yet able to use….. Can wait to get my beast running. -Brad From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
Sent: Sunday, January 22, 2012 12:24 PM
To: DynoMotion@yahoogroups.com
Subject: Re: [DynoMotion] What is the normal sequence of events when initializing a system? KMotionCNC Users sometimes have only one C program to Initialize and Home their system. But it shouldn't be a big deal for those to strip out the Homing portion if need be. Mach3 Users usually always have separate "Reset" and "Home" C Programs. The Init progam often does other things besides setting parameters such as configuring IO, enabling Axes, DefineCoordSystem(), Enabling Amplifiers, and then often remains in a forever loop to handle things like an MPG, or soft limits, or hardware feedhold inputs, etc... Hey something you might consider is just reading the Init.c file itself and extracting the parameters. I've been meaning to do a similar thing for KMotion.exe. The Screen Parameters-> ClipBoard -> Paste into Init.c thing is too confusing and hard to verify the screen settings and the C code are the same. I think we need ScreensToC and CtoScreens buttons that would automatically parse through the C code and import or export the settings for All the Axes. Hello all,
I am planning to create a mechanism for MM and the new HTML controller that will read the values from the Kflop to determine things like axis parameters, TP params, Interpreter axis map, etc...
This will allow the systems to configure themselves and hopefully allow a current kflop user to get up and running with their existing init.c files.
The problem is I do not know how things are normally used(my machine is still only 90% complete). My largest concern is knowing whether or not the machine is homed during the init, or is the init file a separate c file used only for init.
If it is just a separate file, I can just fire off the init.c and then query the kflop to setup the data structures and the GUI.
Any help understanding the existing process is greatly appreciated.
-Brad Murry |
|
| Group: DynoMotion |
Message: 3348 |
From: Brad Murry |
Date: 1/22/2012 |
| Subject: Re: What is the normal sequence of events when initializing a system |
Hello Tom, I thought about just reading the init.c, but I think it is less work to just query the API for the results. -Brad Murry From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
Sent: Sunday, January 22, 2012 12:24 PM
To: DynoMotion@yahoogroups.com
Subject: Re: [DynoMotion] What is the normal sequence of events when initializing a system? KMotionCNC Users sometimes have only one C program to Initialize and Home their system. But it shouldn't be a big deal for those to strip out the Homing portion if need be. Mach3 Users usually always have separate "Reset" and "Home" C Programs. The Init progam often does other things besides setting parameters such as configuring IO, enabling Axes, DefineCoordSystem(), Enabling Amplifiers, and then often remains in a forever loop to handle things like an MPG, or soft limits, or hardware feedhold inputs, etc... Hey something you might consider is just reading the Init.c file itself and extracting the parameters. I've been meaning to do a similar thing for KMotion.exe. The Screen Parameters-> ClipBoard -> Paste into Init.c thing is too confusing and hard to verify the screen settings and the C code are the same. I think we need ScreensToC and CtoScreens buttons that would automatically parse through the C code and import or export the settings for All the Axes. Hello all,
I am planning to create a mechanism for MM and the new HTML controller that will read the values from the Kflop to determine things like axis parameters, TP params, Interpreter axis map, etc...
This will allow the systems to configure themselves and hopefully allow a current kflop user to get up and running with their existing init.c files.
The problem is I do not know how things are normally used(my machine is still only 90% complete). My largest concern is knowing whether or not the machine is homed during the init, or is the init file a separate c file used only for init.
If it is just a separate file, I can just fire off the init.c and then query the kflop to setup the data structures and the GUI.
Any help understanding the existing process is greatly appreciated.
-Brad Murry |
|
| |
